Auto-Generated Summary

> Provide an extensive summary of the agreements by topic. No need to mention CRs.

Summary of Agreements by Topic

XR-Specific Power Saving Techniques

1. CDRX Enhancements:
• Semi-static solutions are prioritized for aligning CDRX with XR traffic periodicity.
• Dynamic periodicity alignment between CDRX and XR traffic is deprioritized.
• Early stopping of On-Duration timer and multiple active CDRX configurations are not supported.
• DRX enhancements for XR services should not affect other data services.
2. PDCCH Monitoring Enhancements:
• All proposed PDCCH monitoring adaptation schemes need to be compared against Rel-17 PDCCH monitoring adaptation.
• PDCCH monitoring resumption after UL NACK is supported by some companies but lacks consensus.
• Continuous PDCCH skipping and dynamic signaling for additional On-Duration are not supported.
3. General Power Saving Agreements:
• Rel-17 evaluation methodology for XR power saving is used as the baseline.
• Companies are encouraged to provide detailed evaluation results for proposed enhancements.

XR-Specific Capacity Enhancements

1. Multi-PUSCH CG Configuration:
• Multi-PUSCH CG is supported for Type-1 and Type-2 configured grants.
• HARQ process IDs for multi-PUSCH CG are determined based on legacy procedures with specific formulas.
• Repetition and TB processing over multiple slots are not supported for multi-PUSCH CG.
• The same SLIV is used across slots when multi-PUSCH CG is configured.
2. UTO-UCI Indication:
• UTO-UCI is applicable only to valid CG PUSCH transmission occasions.
• UTO-UCI indication is enabled by configuration of an RRC parameter.
• UTO-UCI and HARQ-ACK are jointly encoded when applicable, with HARQ-ACK bit sequence concatenated after UTO-UCI bit sequence.
3. Higher Layer Parameters:
• Range values for RRC parameters like Nu (size of bitmap) and UTO_period are defined.
• UTO_offset is not supported in Rel-18.
• Joint release of multiple CG configurations is supported, subject to UE capability.
4. General Capacity Agreements:
• Rel-17 evaluation methodology for XR capacity enhancement is used as the baseline.
• Companies are encouraged to provide simulation results using the capacity Excel sheet attached to TR 38.838.

Maintenance of XR Enhancements

1. HARQ Process ID Determination:
• Valid configured PUSCH grants are defined from the perspective of valid transmissions, excluding collisions with DL symbols or SSB.
• HARQ process ID determination aligns with RAN2 specifications.
2. Multi-PUSCH CG Configuration:
• Multi-PUSCH CG is not supported for operation on shared spectrum.
• Existing ConfiguredGrantConfigIndex is used to indicate the index of multiple CG configurations.
3. UTO-UCI Multiplexing:
• Procedures for CG-UCI are reused for UTO-UCI when applicable.
• Polar code is applied for joint encoding of UTO-UCI and HARQ-ACK when the combined sequence exceeds 11 bits.
4. General Maintenance Agreements:
• Clarifications are added to ensure consistent UE behavior and alignment between RAN1 and RAN2 specifications.

General Agreements

1. Evaluation Methodologies:
• Rel-17 methodologies for power saving and capacity enhancements are used as baselines.
• Companies are encouraged to provide detailed and reproducible evaluation results.
2. Specification Impact:
• Any proposed enhancements must be evaluated for performance gains, complexity, and specification impact.
• Features without consensus or evaluation results are deprioritized.
3. Coordination with RAN2:
• Agreements and findings are communicated to RAN2 via LS to ensure alignment across working groups.

This summary captures the key agreements across power saving, capacity enhancements, and maintenance topics for XR enhancements in Rel-18.